Product Change Notification Number PCN 03092020-001
MultiTech announces updated firmware versions for the
MultiTech® Conduit® family products, including:
I. Overview
MultiTech announces updated firmware versions for the
MultiTech® Conduit® family products, including:
The purpose of this Software Notification is to alert customers that
updated code is available for evaluation and to provide customers
important information on this new release.
New mPower AEP Versions:
NOTE: mPower AEP 5.1.5 corrects a critical issue that was discovered in mPower AEP
5..2 Customers who have upgraded their firmware to mPower AEP 5.1.2 or have
receiveed hardware with mPower AEP 5.1.2 already installed should understand the
critical issue and upgrade these devices to mPower AEP 5.1.5
II. Schedule
There are mutliple versions of mPower Edge Intelligence firmware available for customer evaluation and final
release.
III. mPower™ Edge Intelligence
mPower™ Edge Intelligence is MultiTech´s embedded software offering, building on the popular application
enablement platform, to deliver programmability network flexibbility, enhanced security and manageability for
scalable Industrial Internet of THings (IIoT) solutions.
mPower Edge Intelligence simplifies integration with a variety of popular upstream IoT platforms to streamline
edge-to-cloud data management and analytics, while also providing the programmability ad processing
capability to execute critical task at the dge of the network to reduce atency, control network and cloud
services costs, and ensure core functionality - even in instances when network connectivity may not be available
In respone to evolving customer security requirements, mPower Edge Intelligence incorporates a host of security
features including signed firmware validation enhanced firewall and VPN settings, secure authentication and
more
IV. Models Impacted
The following Conduit models are impacted by these firmware updates:
V. mPower AEP 5.1.5 Overview
Minimum System Requriements (MTCAP AEP 5.1.5, MTCDT AEP 5.1.5)
To install mPower AEP 5.1.5, the Conduit Gateway be upgraded to mPower AEP 5.0.0 or higher. Customers that
are running earlier versions of mPower should use the following upgrade process:
Bug Fixes (MTCAP AEP 5.1.5, MTCDT AEP 5.1.5): Firmware vresion mPower AEP 5.1.5 includes the follwing bug fixes.
1. Critical Isssue: LoRa Packet Forward Log - Script Rotate
2. Knwon Issue: Parity packet index was still using 0, which will break FUOTA for compliant devices
3. Known Issue: When using a roaming SIM card, cellular PPP issues are experienced
4. Known Issue: In firmware version mPower AEP 5.1.2, a bug was introduced that prevented the ModBus
gateway code from executing, leading to the feature not working at all. This issue has been corrected in
mPower AEP 5.1.5
Feature Enhancements MTCAP AEP 5.1.5, MTCDT AEP 5.1.5):
Firmware version AEP 5.1.5 includes the following new features and feature enhancements.
VII. Upgrading Firmware Using DeviceHQ
At any time in the upgrade process, customers can send an email to support@multitech.com or call
+763-717-5863.
DeviceHQ can updated the firmware running on any supported device. Since devices have no live connection to
DeviceHQ, firmware Updates are made the next time a device checks into DeviceHQ.
Instructions
1. Visit https://www.devicehq.com
2. Sign in to your account using your email address andd password
3. Click Devices. The device list page opens.
4. Click the name of the device you want to update. You an update firmware on filtered devices or selected
devices.
firmware file. A confirmation message appears, informing you that the new firmware is to be applied to the deivce when the deivce next checks in.
6. To confirm that you wnat to update firmware click OK.
NOTE: To schedule multiple devices at once, see help file within DeviceHQ
VIII. Updating Firmware Using Shell Script Update br> A shelll Script Update can be performed by customers interested in updating the LoRa Logging Package provided in
mPower MTCAP AEP 5.1.2 and MTCDT AEP 5.1.2
NOTE:
The Shell Script Update is not a full mPower firmware image, it is only designed to resolve Critical Issue 1 and
should only be used to update mPower MTCAP AEP 5.1.2 and mPower MTCDT AEP 5.1.2
1. Visit https://www.multitech.net/developer/downloads/
2. Scoll down to LoRaWAN Downloads. There you will find the link: Lora Logging 1.0-r3
3. Click on the link to download the IPK file.
4. The file must be uploaded to the device. We reommoend using WinSCP for seucre file transfer.
https://winscp.net/eng/index.php
5. Load WinSCP to the root of the connection
6. Acces the device using SSH and run the following command
sudo opkg install lora-logging_1.0-r3.0_arm926ejste.ipk
You should be asked to enter your password
7. WinSCP will run and load the IPK file.
IX. Ordering Part Numbers Impacted
The following ordering part numbers are impacted by these updates:
X. Conduit® IoT Gateways
Conduit® family of products is the industrys most configurable, manageable and scalable cellular
communications gateways for industrial IoT appplications. Network engineers can remotely configure and optimize
their Conduit performance through DeviceHQ®, the worlds first IoT Application Store and Device Management
platform. The award-winning Conduit series comes in three variants designed to address specific IoT gateway use cases:
XI. Additonal Information If you have any questions regarding this Product Change/Software Release Notification, please contact your
MultiTech Sales Representative
MultiTech announces updated firmware versions for the
MultiTech® Conduit® family products, including:
- Conduit® AP Access Point
- Conduit® IoT Programmable Gateway
- Conduit® IP67 Base Station
The purpose of this Software Notification is to alert customers that
updated code is available for evaluation and to provide customers
important information on this new release.
New mPower AEP Versions:
- MTCAP AEP 5.1.5 (Conduit AP Acces Point)
- MTCDT AEP 5.1.5 (Conduit Gateway and Conduit IP67 Base
Station)
NOTE: mPower AEP 5.1.5 corrects a critical issue that was discovered in mPower AEP
5..2 Customers who have upgraded their firmware to mPower AEP 5.1.2 or have
receiveed hardware with mPower AEP 5.1.2 already installed should understand the
critical issue and upgrade these devices to mPower AEP 5.1.5
II. Schedule
There are mutliple versions of mPower Edge Intelligence firmware available for customer evaluation and final
release.
- Downloadable Versions
- MTCAP AEP 5.1.5 Availability: Early March
- MTCDT AEP 5.1.5 Availability: Early March
- Manufacturing
- See Ordering Numbers Impacted for details on when MTCAP AEP 5.1.5 and MTCDT AEP 5.1.5 will
be available for different devices
- DeviceHQ®
- Cloud-based IoT Device Management
- mPower AEP 5.1.5 Availability: Early March
| Note: Critical Isue 1 can also be corrected by performing a Shell Script Updates as outlined in the insturcitons below |
III. mPower™ Edge Intelligence
mPower™ Edge Intelligence is MultiTech´s embedded software offering, building on the popular application
enablement platform, to deliver programmability network flexibbility, enhanced security and manageability for
scalable Industrial Internet of THings (IIoT) solutions.
mPower Edge Intelligence simplifies integration with a variety of popular upstream IoT platforms to streamline
edge-to-cloud data management and analytics, while also providing the programmability ad processing
capability to execute critical task at the dge of the network to reduce atency, control network and cloud
services costs, and ensure core functionality - even in instances when network connectivity may not be available
In respone to evolving customer security requirements, mPower Edge Intelligence incorporates a host of security
features including signed firmware validation enhanced firewall and VPN settings, secure authentication and
more
IV. Models Impacted
The following Conduit models are impacted by these firmware updates:
- Conduit® IoT Programmable Gateways
- Conduit® IoT Programmable Gateways with LoRa Accessory Card
- Conduit® IP67 Base Stations
- Conduit® IP67 Geolocation Base Station
- Conduit® AP Access Point
V. mPower AEP 5.1.5 Overview
Minimum System Requriements (MTCAP AEP 5.1.5, MTCDT AEP 5.1.5)
To install mPower AEP 5.1.5, the Conduit Gateway be upgraded to mPower AEP 5.0.0 or higher. Customers that
are running earlier versions of mPower should use the following upgrade process:
- mPower AEP 1.7.4
- Upgrade to Mower AEP 5.0.0
- Install mPower AEP 5.1.5
- mPower AEP 1.6.4
- Upgrade to mPower AEP 1.7.4
- Upgrade to mPower AEP 5.0.0
- Install mPower AEP 5.1.5
- mPoer versions earlier than mPower AEP 1.6.4
- Upgrade to mPower AEP 1.6.4
- Upgrade to mPower AEP 1.7.4
- Upgrade to mPower AEP 5.0.0
- Install mPower AEP 5.1.5
Bug Fixes (MTCAP AEP 5.1.5, MTCDT AEP 5.1.5): Firmware vresion mPower AEP 5.1.5 includes the follwing bug fixes.
1. Critical Isssue: LoRa Packet Forward Log - Script Rotate
- Overview
- Ocurs when the device LoRa Mode is set to LoRa Packet Forwarder
- As more LoRa data is sent to the device the LoRa Packet Forward Log File (lora-pkt-fwd-1.log)
continues to grow - The log rotate process eventually fails to totate the packet forwarder lots
- Logs are located in RAM, eventually all availablee RAM is used up by the log file
- The LoRa Packet Forwarder is now unresponsive and sends no packets until the deivce is power-cycled
- Issue only exists in MTCAP AEP 5.1.2 and MTCDT AEP 5.1.2, which was released to a limited number of
devices - Issue does not exist when using a third-party LoRa Packet Forwarder
- Resolution:
- Customers have two ways of resovling this cirital issue
- Update the entire firmware image to MTCAP AEP 5.1.5 or MTCDT AEP 5.1.5 using the
web interface or Device HQ - Update only the LoRa Logging Package using a Shell Script Update
- The following devices were shipping from MultiTech and are impacted by this critical issue
| Model Name | Ordering Part Numbers | |
| Conduit® IoT Programmable Gateways | ||
| MTCDT-L4E1-246A-EU-GB MTCDT-L4E1-247A-EU-GB |
MTCDT-L4N1-246A-US MTCDT-L4N1-247A-US |
MTCDT-L4N1-247A |
| Conduit® IoT Programmable Gateways with LoRa Accessory Cards | ||
| MTCDT-L4E1-246A-868-EU-GB MTCDT-L4E1-247A-868-EU-GB |
MTCDT-L4E1-246A-915-EU-GB MTCDT-L4E1-247A-915-EU-GB |
MTCDT-L4N1-246A-915-US MTCDT-L4N1-247A-915-US |
| Conduit® IP67 Base Stations | ||
| MTCDTIP-L4E1-266A-868 MTCDTIP-L4E1-267A-868 |
MTCDTIP-L4E1-266A-915 | MTCDTIP-L4N1-266A-915 MTCDTIP-L4N1-267A-915 |
| Conduit® IP67 Geolocation Base Station | ||
| MTCDTIP-L4E1-270A-868 | MTCDTIP-L4N1-270A-915 | MTCDTIP-L4N1-275A-915 |
| Conduit® AP Access Point | ||
| MTCAP-868-041A | MTCAP-L4E1-868-001A | MTCAP-LNA3-915-041A |
| Hardware Status |
Manufacturing Updates |
Comments | |
| (1) | New | March 2020 |
|
- Customers who have updated Near-End-of-life (NEOL) devices or existing devices to mPower AEP
5.1.2 are als impacted - See Ordering Part Numbers Impacted for a complete list of impacted devices
2. Knwon Issue: Parity packet index was still using 0, which will break FUOTA for compliant devices
- Issue exists in MTCAP AEP 5.1.1 and MTCDT AEP 5.1.1 versions and AEP 5.1.0 BETA versions only
- AEP 5.1.1 was an intermediate release for select LTE Category 4 (-L4E1) models
- AEP 5.1.0 BETA was a beta release for select LTE Category 4 (-L4E1) models
- Issue fixed in MTCAP AEP 5.1.5 and MTCDT AEP 5.1.5
3. Known Issue: When using a roaming SIM card, cellular PPP issues are experienced
- Issue exists in MTCAP AEP 5.1.0 and MTCDT AEP 5.1.0 versions
- Issue Fixed in MTCAP AEP 5.1.5 and MTCDT AEP 5.1.5
4. Known Issue: In firmware version mPower AEP 5.1.2, a bug was introduced that prevented the ModBus
gateway code from executing, leading to the feature not working at all. This issue has been corrected in
mPower AEP 5.1.5
Feature Enhancements MTCAP AEP 5.1.5, MTCDT AEP 5.1.5):
Firmware version AEP 5.1.5 includes the following new features and feature enhancements.
- Hardware Support
- Radio support updated for the following cellular technologies
Cellular WAN Support Wireless Carrier 4G-LTE Category 4 North America (_L4N1 models) ATT
Verizon
- Feature Enhancements
- First-Time Setup
- Setup Wizard: option added for Remote Management - DeviceHQ
- Network Interfaces
- Added support for IPv6 in several specific network configurations
Network Interface IP Modde Bridge (Br0) Static Ethernet (Eth0) Static
DHCP ClientPPP Interface (ppp0) PPP
PPP - Addresses Only - IPv6 WAN on cellular only
- Added support for IPv6 in several specific network configurations
- Global DNS
- Option added to configure the hostname of the device
- Dynamic Host Confiuration Protocol (DHCP) Server
- Support added for configuring and enabling IPv6 DHCP server(s)
- Setting up Wi-Fi as a WAN
- Support added for connecting to hidden SSID networks
- Updated Destination and Source Interface Firewall Rules now include OPENVPN option
- Pre-routing Rules
- Post-routing Rules
- Input filter rules
- Inbound forwarding rules
- Output filter rules
- Added Celular Configuration Fields
- Cellular Mode: Select the cellular mode from the drop-down menu based on the cellular radio
module in the device (Auto (default), LTE only, LTE prefer, 2G only, 3G only, or 3G prefer) - Modem Configuration (allows user to switch firmware from one MNO network to antoher).
- L4N1 Models: AT&T (defaullt) or Verizon
- Cellular Mode: Select the cellular mode from the drop-down menu based on the cellular radio
- Added Password COmplexity Rules: Administrative user can choose rules and limitations for user
passwords, including:- Minimum length of passwords
- Upper and lower case requirements
- Special Characers (non-alphanumeric)
- Characters that are not permitted
- Two Modes are avaiable:
- Default Mode: Minimum character length and specific number of characters
- Credit Mode. Credits are granted for each password character and extra credits are applied
for certain character classes. Administrators specify a minimum of classes. Longer
passwords are the strongest
- Configuring Device Access: How the deivce can be accessed as well as security features that
decrease susceptibility and malicious activity.- Addded remote SSH server
- Managing Devices Remotely (DeviceHQ): Updates to DeviceHQ Check-In Settings
- Single Check-In: Configure device to checkin to DeviceHQ at a specific date and time
- Repeatable Check-In: Configure device to check-in to DeviceHQ at a specific time daily or on a
specific day of the week
- Upgrading Firmware form MultiTech website or DeviceHQ
- Signed Firmware Validation is automatically used once it is enabled after upgrading from
version 5.1 and higher
- Signed Firmware Validation is automatically used once it is enabled after upgrading from
- LoRaWAN
- Spectral scan support with reporting to Lens
- MultiCast support for Class B
- MultiCast field added to device session:
- 0: None
- 1: Class B
- 2: Class C
- No longer need to set Uplink Counter to 1 for multicast sessions to schedule downlinks
- Session can be modified for managing MultiCast Sessions
- LoRaWAN 1.0.4 supports
- Join Server nonce counters
- Includes validation of end-device DevNonce counter if LoRaWAN 1.0.4
support is specified in Device Profile - Use AU/US LinkAdrReq sub-band channell mask commands if LoRaWAN 1.0.4 suppots
is specified in Device Profile
- LoRaWAN FUOTA
- Customers using FUOTA should be advised to upgrade to AEP 5.1.5
- If a customer is using AEP 5.0.x with FUOTA to Dot v3.2.x, then the Dot firmware should be
updated to the next release v3.3.x before updating the hardware to AEP 5.1.5 - mPower 5.1.1 compatible Beta firmware for mDot/xDot is avialable at
https://github.com/MultiTechSystems/Dot-AT-Firmware - FUOTA is being updated to be compliant with LoRa Alliance specifications
- FUOTA has been testet with the following implementations
- Arm Mbed (https://github.com/armmbed/mbed-os-example-lorawan-fuota)
- Semtech/Stackforce (https://github.com/Lora-net/LoRaMac-node)
- MultiTech Dts v3.3.x (Release Date TBD)
- The update will break compatibility with MutliTech Dot v3.2.x as issues were found
- Fragment and Parity indexes started at/li>
- Key Encryption had the encrypt/decrypt operations flipped, decrypt was incorrectly
used on the end-device - Status messages were incorrect
VII. Upgrading Firmware Using DeviceHQ
At any time in the upgrade process, customers can send an email to support@multitech.com or call
+763-717-5863.
DeviceHQ can updated the firmware running on any supported device. Since devices have no live connection to
DeviceHQ, firmware Updates are made the next time a device checks into DeviceHQ.
Instructions
1. Visit https://www.devicehq.com
2. Sign in to your account using your email address andd password
3. Click Devices. The device list page opens.
4. Click the name of the device you want to update. You an update firmware on filtered devices or selected
devices.
- If you select individual devices, you update firmware on selected devices or the filtered devices.
- If you do not select devices you update the firmware on the filtered devices.
firmware file. A confirmation message appears, informing you that the new firmware is to be applied to the deivce when the deivce next checks in.
6. To confirm that you wnat to update firmware click OK.
VIII. Updating Firmware Using Shell Script Update br> A shelll Script Update can be performed by customers interested in updating the LoRa Logging Package provided in
mPower MTCAP AEP 5.1.2 and MTCDT AEP 5.1.2
NOTE:
The Shell Script Update is not a full mPower firmware image, it is only designed to resolve Critical Issue 1 and
should only be used to update mPower MTCAP AEP 5.1.2 and mPower MTCDT AEP 5.1.2
1. Visit https://www.multitech.net/developer/downloads/
2. Scoll down to LoRaWAN Downloads. There you will find the link: Lora Logging 1.0-r3
3. Click on the link to download the IPK file.
4. The file must be uploaded to the device. We reommoend using WinSCP for seucre file transfer.
https://winscp.net/eng/index.php
5. Load WinSCP to the root of the connection
6. Acces the device using SSH and run the following command
sudo opkg install lora-logging_1.0-r3.0_arm926ejste.ipk
You should be asked to enter your password
7. WinSCP will run and load the IPK file.
IX. Ordering Part Numbers Impacted
The following ordering part numbers are impacted by these updates:
| Model Name | Orderin Part Numbers | |
| Conduit® IoT Programmable Gateways | ||
| MTCDT-246A-US-EU-GB MTCDT-247A-US-EU-GB MTCDT-H5-246A-US-EU-GB MTCDT-H5-247A-US-EU-GB MTCDT-LAT1-246A-US MTCDT-LAT1-247A |
MTCDT-LAT1-247A-US MTCDT-LVW2-246A-US MTCDT-LVW2-247A MTCDT-LVW2-247A-US MTCDT-L4N1-246A-US MTCDT-L4N1-246A-US |
MTCDT-L4N1-247A-US MTCDT-L4N1-247A MTCDT-L4E1-246A-EU-GB MTCDT-L4E1-247A-EU-GB MTCDT-LAP3-246A-AU MTCDT-LSP3-246A-US |
| Conduit® IoT Programmable Gateways with LoRa Accessory Cards | ||
| MTCDT-246A-868-EU-GB MTCDT-246A-915-US-EU-GB MTCDT-246A-923-JP MTCDT-246A-US-EU-GB-923KR MTCDT-247A-868-EU-GB MTCDT-247A-915-US-EU-GB MTCDT-H5-246A-868-EU-GB |
MTCDT-H5-247A-868-EU-GB MTCDT-H5-247A-915-US MTCDT-LAT1-246A-915-US MTCDT-LAT1-247A-915-US MTCDT-LVW2-246A-915-US MTCDT-LVW2-247A-915-US MTCDT-L4E1-246A-868-EU-GB |
MTCDT-L4E1-246A-915-EU-GB MTCDT-L4E1-247A-868-EU-GB MTCDT-L4E1-247A-915-EU-GB MTCDT-L4N1-246A-915-US MTCDT-L4N1-247A-915-US MTCDT-LAP3-246A-915-AU MTCDT-LAP3-247A-915-AU MTCDT-LSB3-246A-923-JP |
| Conduit® IP67 Base Stations | ||
| MTCDTIP-266A-868 MTCDTIP-266A-915 MTCDTIP-266A-915-JP MTCDTIP-266A-923KR MTCDTIP-267A-868 MTCDTIP-267A-915 |
MTCDTIP-LAT1-266A-915 MTCDTIP-LAT1-267A-915 MTCDTIP-LVW2-266A-915 MTCDTIP-LVW2-267A-915 MTCDTIP-L4E1-266A-868 MTCDTIP-L4E1-266A-915 |
MTCDTIP-L4E1-267A-868 MTCDTIP-L4N1-266A-915 MTCDTIP-L4N1-267A-915 MTCDTIP-LAP3-266A-915 MTCDTIP-LAP3-267A-915 MTCDTIP-LSB3-266A-923-JP |
| Conduit® IP67 Geolocation Base Stations | ||
| MTCDTIP-LAT1-270A-915 MTCDTIP-LAT1-275A-915 |
MTCDTIP-LVW2-270A-915 MTCDTIP-LVW2-275A-915 |
MTCDTIP-L4E1-270A-868 MTCDTIP-L4N1-270A-915 MTCDTIP-L4N1-275A-915 |
| Conduit® AP Access Points | ||
| MTCAP-868-001A MTCAP-868-041A MTCAP-915-001A |
MTCAP-915-041A MTCAP-L4E1-868-001A MTCAP-LNA3-915-001A |
MTCAP-LNA3-915-041A MTCAP-LSP3-915-001A MTCAP-LSP3-915-041A |
| Hardware Status | Manufacturing Updates | Comments | |
| (1) | New | March 2020 |
|
| (2) | NEOL | N/A |
|
| (3) | Existing | 60 - 90 days |
|
X. Conduit® IoT Gateways
Conduit® family of products is the industrys most configurable, manageable and scalable cellular
communications gateways for industrial IoT appplications. Network engineers can remotely configure and optimize
their Conduit performance through DeviceHQ®, the worlds first IoT Application Store and Device Management
platform. The award-winning Conduit series comes in three variants designed to address specific IoT gateway use cases:
- Conduit: Indoor industrial gateway, ideal for environents that require metal casing for protection
against particles and debris and requrire and industrial temperature range - Conduit IP67 Base Station: Outdoor IP67-rated gateway ideal suited for performing in harsh
environments such as rain, snow, extreme heat, and high winds. - Conduit AP: Indoor access pint ideal for commercial environments (e.g., hotels, offices, retail facilities)
to deepen LoRa coverage in difficult to reach places where cell tower or rooftop deployments may not
perform as well.
XI. Additonal Information If you have any questions regarding this Product Change/Software Release Notification, please contact your
MultiTech Sales Representative